Command to Search for Filenames Exceeding 143 Characters?Output exceeding terminal window heightHow to batch...

Line of lights moving in a straight line , with a few following

How to use Palladio font in text body but Computer Modern for Equations?

Compactness of finite sets

Does the unit of measure matter when you are solving for the diameter of a circumference?

Simple function that simulates survey results based on sample size and probability

Using credit/debit card details vs swiping a card in a payment (credit card) terminal

Why doesn't the Earth accelerate towards the Moon?

If a person had control of every single cell of their body, would they be able to transform into another creature?

Count rotary dial pulses in a phone number (including letters)

Statue View: 2, 3, 5, 7

Crossing US border with music files I'm legally allowed to possess

What are the real benefits of using Salesforce DX?

What is quasi-aromaticity?

Which is the common name of Mind Flayers?

Make 24 using exactly three 3s

Should breaking down something like a door be adjudicated as an attempt to beat its AC and HP, or as an ability check against a set DC?

Is there some hidden joke behind the "it's never lupus" running gag in House?

Flying domestically in the US, is my State Issued ID all I need to get past security?

A steel cutting sword?

Plot twist where the antagonist wins

How to pull out the underlying query syntax being used by dataset?

Why does this if-statement combining assignment and an equality check return true?

Employer asking for online access to bank account - Is this a scam?

What does the view outside my ship traveling at light speed look like?



Command to Search for Filenames Exceeding 143 Characters?


Output exceeding terminal window heightHow to batch clean filenames containing invalid charactersSearch/grep ftp remote filenamesMake grep work for special filenamesIs it correct to use certain special characters when naming filenames in Linux?What characters are valid to use in filenames?List of filenames as argument for mplayer => mplayer doesn't recognize the filenamesCharacters best avoided in filenames when used in Bash, e.g. `?`Search for bash commandlinux find command for filenames without extension for unknown extensions






.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ margin-bottom:0;
}







1















So some background first: I am attempting to convert a non-encrypted shared folder into an encrypted one on my Synology NAS and am seeing this error:



Synology NAS Error



So I would like to locate the offending files so that I may rename them. I have come up with the following grep command: grep -rle '[^ ]{143,}' * but it outputs all files with paths greater than 143 characters:



#recycle/Music/TO SORT/music/H/Hooligans----Heroes of Hifi/Metalcore Promotions - Heroes of Hifi - 03 Sly Like a Megan Fox.mp3
...


What I would like is for grep to split on / and then perform its search. Any idea on an efficient command to go about this (directory easily contains hundreds of thousands of files)?










share|improve this question

























  • For a collection of CJK p{} classes, see this stack overflow answer: stackoverflow.com/a/48673340

    – Andrew Domaszek
    24 mins ago


















1















So some background first: I am attempting to convert a non-encrypted shared folder into an encrypted one on my Synology NAS and am seeing this error:



Synology NAS Error



So I would like to locate the offending files so that I may rename them. I have come up with the following grep command: grep -rle '[^ ]{143,}' * but it outputs all files with paths greater than 143 characters:



#recycle/Music/TO SORT/music/H/Hooligans----Heroes of Hifi/Metalcore Promotions - Heroes of Hifi - 03 Sly Like a Megan Fox.mp3
...


What I would like is for grep to split on / and then perform its search. Any idea on an efficient command to go about this (directory easily contains hundreds of thousands of files)?










share|improve this question

























  • For a collection of CJK p{} classes, see this stack overflow answer: stackoverflow.com/a/48673340

    – Andrew Domaszek
    24 mins ago














1












1








1


1






So some background first: I am attempting to convert a non-encrypted shared folder into an encrypted one on my Synology NAS and am seeing this error:



Synology NAS Error



So I would like to locate the offending files so that I may rename them. I have come up with the following grep command: grep -rle '[^ ]{143,}' * but it outputs all files with paths greater than 143 characters:



#recycle/Music/TO SORT/music/H/Hooligans----Heroes of Hifi/Metalcore Promotions - Heroes of Hifi - 03 Sly Like a Megan Fox.mp3
...


What I would like is for grep to split on / and then perform its search. Any idea on an efficient command to go about this (directory easily contains hundreds of thousands of files)?










share|improve this question
















So some background first: I am attempting to convert a non-encrypted shared folder into an encrypted one on my Synology NAS and am seeing this error:



Synology NAS Error



So I would like to locate the offending files so that I may rename them. I have come up with the following grep command: grep -rle '[^ ]{143,}' * but it outputs all files with paths greater than 143 characters:



#recycle/Music/TO SORT/music/H/Hooligans----Heroes of Hifi/Metalcore Promotions - Heroes of Hifi - 03 Sly Like a Megan Fox.mp3
...


What I would like is for grep to split on / and then perform its search. Any idea on an efficient command to go about this (directory easily contains hundreds of thousands of files)?







command-line filenames






share|improve this question















share|improve this question













share|improve this question




share|improve this question








edited 41 mins ago







Stunner

















asked 2 hours ago









StunnerStunner

1084




1084













  • For a collection of CJK p{} classes, see this stack overflow answer: stackoverflow.com/a/48673340

    – Andrew Domaszek
    24 mins ago



















  • For a collection of CJK p{} classes, see this stack overflow answer: stackoverflow.com/a/48673340

    – Andrew Domaszek
    24 mins ago

















For a collection of CJK p{} classes, see this stack overflow answer: stackoverflow.com/a/48673340

– Andrew Domaszek
24 mins ago





For a collection of CJK p{} classes, see this stack overflow answer: stackoverflow.com/a/48673340

– Andrew Domaszek
24 mins ago










3 Answers
3






active

oldest

votes


















2














Try:



find /your/path | grep -E '[^/]{143,}$'





share|improve this answer































    3














    At least with GNU find you can use a -regex test:



    find . -regextype posix-extended -regex '.*/[^/]{143,}$'


    or



    find . -regextype egrep -regex '.*/[^/]{143,}$'


    or



    find . -regextype posix-basic -regex '.*/[^/]{143,}$'


    etc. (there may be other regextypes that support { } intervals).






    share|improve this answer































      0














      If you've already got a locate db, it is very fast at this.



      locate --regex '.*/[^/]{143,}$'





      share|improve this answer
























        Your Answer








        StackExchange.ready(function() {
        var channelOptions = {
        tags: "".split(" "),
        id: "106"
        };
        initTagRenderer("".split(" "), "".split(" "), channelOptions);

        StackExchange.using("externalEditor", function() {
        // Have to fire editor after snippets, if snippets enabled
        if (StackExchange.settings.snippets.snippetsEnabled) {
        StackExchange.using("snippets", function() {
        createEditor();
        });
        }
        else {
        createEditor();
        }
        });

        function createEditor() {
        StackExchange.prepareEditor({
        heartbeatType: 'answer',
        autoActivateHeartbeat: false,
        convertImagesToLinks: false,
        noModals: true,
        showLowRepImageUploadWarning: true,
        reputationToPostImages: null,
        bindNavPrevention: true,
        postfix: "",
        imageUploader: {
        brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
        contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
        allowUrls: true
        },
        onDemand: true,
        discardSelector: ".discard-answer"
        ,immediatelyShowMarkdownHelp:true
        });


        }
        });














        draft saved

        draft discarded


















        StackExchange.ready(
        function () {
        StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f521096%2fcommand-to-search-for-filenames-exceeding-143-characters%23new-answer', 'question_page');
        }
        );

        Post as a guest















        Required, but never shown

























        3 Answers
        3






        active

        oldest

        votes








        3 Answers
        3






        active

        oldest

        votes









        active

        oldest

        votes






        active

        oldest

        votes









        2














        Try:



        find /your/path | grep -E '[^/]{143,}$'





        share|improve this answer




























          2














          Try:



          find /your/path | grep -E '[^/]{143,}$'





          share|improve this answer


























            2












            2








            2







            Try:



            find /your/path | grep -E '[^/]{143,}$'





            share|improve this answer













            Try:



            find /your/path | grep -E '[^/]{143,}$'






            share|improve this answer












            share|improve this answer



            share|improve this answer










            answered 1 hour ago









            Jim L.Jim L.

            52015




            52015

























                3














                At least with GNU find you can use a -regex test:



                find . -regextype posix-extended -regex '.*/[^/]{143,}$'


                or



                find . -regextype egrep -regex '.*/[^/]{143,}$'


                or



                find . -regextype posix-basic -regex '.*/[^/]{143,}$'


                etc. (there may be other regextypes that support { } intervals).






                share|improve this answer




























                  3














                  At least with GNU find you can use a -regex test:



                  find . -regextype posix-extended -regex '.*/[^/]{143,}$'


                  or



                  find . -regextype egrep -regex '.*/[^/]{143,}$'


                  or



                  find . -regextype posix-basic -regex '.*/[^/]{143,}$'


                  etc. (there may be other regextypes that support { } intervals).






                  share|improve this answer


























                    3












                    3








                    3







                    At least with GNU find you can use a -regex test:



                    find . -regextype posix-extended -regex '.*/[^/]{143,}$'


                    or



                    find . -regextype egrep -regex '.*/[^/]{143,}$'


                    or



                    find . -regextype posix-basic -regex '.*/[^/]{143,}$'


                    etc. (there may be other regextypes that support { } intervals).






                    share|improve this answer













                    At least with GNU find you can use a -regex test:



                    find . -regextype posix-extended -regex '.*/[^/]{143,}$'


                    or



                    find . -regextype egrep -regex '.*/[^/]{143,}$'


                    or



                    find . -regextype posix-basic -regex '.*/[^/]{143,}$'


                    etc. (there may be other regextypes that support { } intervals).







                    share|improve this answer












                    share|improve this answer



                    share|improve this answer










                    answered 1 hour ago









                    steeldriversteeldriver

                    39.2k45491




                    39.2k45491























                        0














                        If you've already got a locate db, it is very fast at this.



                        locate --regex '.*/[^/]{143,}$'





                        share|improve this answer




























                          0














                          If you've already got a locate db, it is very fast at this.



                          locate --regex '.*/[^/]{143,}$'





                          share|improve this answer


























                            0












                            0








                            0







                            If you've already got a locate db, it is very fast at this.



                            locate --regex '.*/[^/]{143,}$'





                            share|improve this answer













                            If you've already got a locate db, it is very fast at this.



                            locate --regex '.*/[^/]{143,}$'






                            share|improve this answer












                            share|improve this answer



                            share|improve this answer










                            answered 31 mins ago









                            Andrew DomaszekAndrew Domaszek

                            1805




                            1805






























                                draft saved

                                draft discarded




















































                                Thanks for contributing an answer to Unix & Linux Stack Exchange!


                                • Please be sure to answer the question. Provide details and share your research!

                                But avoid



                                • Asking for help, clarification, or responding to other answers.

                                • Making statements based on opinion; back them up with references or personal experience.


                                To learn more, see our tips on writing great answers.




                                draft saved


                                draft discarded














                                StackExchange.ready(
                                function () {
                                StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2funix.stackexchange.com%2fquestions%2f521096%2fcommand-to-search-for-filenames-exceeding-143-characters%23new-answer', 'question_page');
                                }
                                );

                                Post as a guest















                                Required, but never shown





















































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown

































                                Required, but never shown














                                Required, but never shown












                                Required, but never shown







                                Required, but never shown







                                Popular posts from this blog

                                Taj Mahal Inhaltsverzeichnis Aufbau | Geschichte | 350-Jahr-Feier | Heutige Bedeutung | Siehe auch |...

                                Baia Sprie Cuprins Etimologie | Istorie | Demografie | Politică și administrație | Arii naturale...

                                Nicolae Petrescu-Găină Cuprins Biografie | Opera | In memoriam | Varia | Controverse, incertitudini...